Thanks, this looks really clean!

Really only have one comment which is, I would love to have a way to detect whether the OpenOCD that CMake has found is the Nuvoton version and not the standard version. Otherwise it would be all too easy to accidentally have the wrong one on your PATH. Is there a specific version number that your OpenOCD builds report?

Nuvoton customized openocd will fix version number to 0.10.022. Hopefully it can be used to tell from standard:

$ openocd --version
Open On-Chip Debugger 0.10.022.0-dev-00493-gd6db465b-dirty (2023-12-14-15:04)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html

Hmm, next step would be updating FindOpenOCD.cmake to check the version number. I should be able to do that sometime within the next week.

Okay once #340 is merged, you should be able to add code like

set(OPENOCD_VERSION_RANGE 0.10.022...0.10.22)

in each of the upload method config files

Also @ccli8 I have invited you to be a member of the mbed-ce organization on github! Thanks for all your contributions! This should give you access to non-protected branches on the main repository, let you edit the wiki, and let you review PRs.

have invited you to be a member of the mbed-ce organization on github! Thanks for all your contributions! This should give you access to non-protected branches on the main repository, let you edit the wiki, and let you review PRs.

@multiplemonomials Thanks, we can make mbed-ce prominent and lasting.

Following #340, added openocd version requirement (for Nuvoton fork version) into each config files:

set(OPENOCD_VERSION_RANGE 0.10.022...0.10.22)